Release 10.1A: OpenEdge Application Server:
Administration

Disabling access to all Web services, to all WSDL, or to all WSA administration

Given a WSA instance, you can disable access to all of its Web services, to all of its WSDL, or to all of its WSA administration. The technique for doing so depends on whether the WSA instance resides locally (on the AdminServer machine) or remotely (not on the AdminServer machine).

If the WSA instance resides locally, using Progress Explorer, highlight the WSA instance, right-click, and choose Properties. Select Security to bring up the Security panel. Then, select the fields on the Security panel to disable access to all Web services, all WSDL, or all WSA administration, as desired. For more information on accessing the Security panel, see the "Controlling access to Web services, WSDL, and WSA administration using user-authorization role-names" section.

If the WSA instance is remote, using a text editor, edit the ubroker.properties file. In the section for the WSA instance, for each function that you want to disable, set the corresponding property, shown in Table 7–6.

Table 7–6: Disabling access to Web services, WSDL, and administration

To disable access to ...	Set this property ...	To ...
Web services	webAppEnabled	0
WSDL	enableWsdl	0
WSA administration	adminEnabled	0

For more information on the properties of a WSA instance, see the comments in the ubroker.properties file.

Note: If you disable all WSA administration access while the WSA instance is running, you must stop and restart the JSE to re-enable WSA administration access.